Skip to content

NO-ISSUE: align statefulset/log-scan tests with the main-branch versions - #7363

Open
agullon wants to merge 1 commit into
openshift:release-5.0from
agullon:sync-7326-extra-release-5.0
Open

NO-ISSUE: align statefulset/log-scan tests with the main-branch versions#7363
agullon wants to merge 1 commit into
openshift:release-5.0from
agullon:sync-7326-extra-release-5.0

Conversation

@agullon

@agullon agullon commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Summary

The test/script consolidation PR merged to release-5.0 (#7327) before two follow-up refinements landed on its main-branch equivalent (#7326). This brings those two refinements to release-5.0 so the branches stay consistent. Test-only.

Changes

  • otp-workloads/statefulset-pvc.robot — wait for the StatefulSet via microshift healthcheck --namespace ${NAMESPACE} --statefulsets hello-statefulset --timeout 5m instead of the oc wait on a named pod (Wait Until Resource Exists + Named Pod Should Be Ready). Cleaner and uses the product healthcheck directly (--statefulsets is supported on release-5.0, pkg/cmd/healthcheck.go). Renames ${POD_NAME}${STATEFULSET_NAME}.
  • standard2/log-scan.robot — rename Boot And Scan JournalService Startup And Scan Journal and Scan Boot JournalScan Service Startup Journal (plus wording), since the test restarts the MicroShift service rather than rebooting the host.

Testing

  • robocop check + format clean on both suites.

Notes

Backport of the delta between #7326 (main) and the already-merged #7327 (release-5.0).

The consolidation PR was merged to release-5.0 (openshift#7327) before two follow-up
refinements landed on the main-branch equivalent (openshift#7326). Bring those over so
the two branches stay consistent:

- otp-workloads/statefulset-pvc: use `microshift healthcheck --statefulsets`
  to wait for the StatefulSet instead of the oc-wait-on-named-pod workaround
  (the --statefulsets flag is supported on release-5.0).
- standard2/log-scan: rename "Boot And Scan Journal"/"Scan Boot Journal" to
  "Service Startup And Scan Journal"/"Scan Service Startup Journal" (the test
  restarts the service, it does not reboot the host).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

pre-commit.check-secrets: ENABLED
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 10, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@agullon: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

The test/script consolidation PR merged to release-5.0 (#7327) before two follow-up refinements landed on its main-branch equivalent (#7326). This brings those two refinements to release-5.0 so the branches stay consistent. Test-only.

Changes

  • otp-workloads/statefulset-pvc.robot — wait for the StatefulSet via microshift healthcheck --namespace ${NAMESPACE} --statefulsets hello-statefulset --timeout 5m instead of the oc wait on a named pod (Wait Until Resource Exists + Named Pod Should Be Ready). Cleaner and uses the product healthcheck directly (--statefulsets is supported on release-5.0, pkg/cmd/healthcheck.go). Renames ${POD_NAME}${STATEFULSET_NAME}.
  • standard2/log-scan.robot — rename Boot And Scan JournalService Startup And Scan Journal and Scan Boot JournalScan Service Startup Journal (plus wording), since the test restarts the MicroShift service rather than rebooting the host.

Testing

  • robocop check + format clean on both suites.

Notes

Backport of the delta between #7326 (main) and the already-merged #7327 (release-5.0).

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@coderabbitai

coderabbitai Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 195112f1-1296-4a79-ab00-ee1712b4f587

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from copejon and jogeo September 10, 2026 09:06
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 10, 2026
@agullon

agullon commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

/retest
/pipeline required

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-tests
/test e2e-aws-tests-arm
/test e2e-aws-tests-bootc-arm-el10
/test e2e-aws-tests-bootc-arm-el9
/test e2e-aws-tests-bootc-el10
/test e2e-aws-tests-bootc-el9

@agullon

agullon commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-release
/test e2e-aws-tests-release-arm
/test e2e-aws-tests-bootc-release-el9
/test e2e-aws-tests-bootc-release-el10
/test e2e-aws-tests-bootc-release-arm-el9
/test e2e-aws-tests-bootc-release-arm-el10

@agullon

agullon commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

/label jira/valid-bug
/label backport-risk-assessed
/verified by CI

@openshift-ci openshift-ci Bot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Sep 10, 2026
@pmtk

pmtk commented Sep 10, 2026

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 10, 2026
@openshift-ci

openshift-ci Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, pmtk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@agullon

agullon commented Sep 10, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci

openshift-ci Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

@agullon: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-tests-bootc-release-arm-el9 89ff01d link true /test e2e-aws-tests-bootc-release-arm-el9
ci/prow/e2e-aws-tests-bootc-release-el9 89ff01d link true /test e2e-aws-tests-bootc-release-el9
ci/prow/e2e-aws-tests-bootc-release-arm-el10 89ff01d link true /test e2e-aws-tests-bootc-release-arm-el10
ci/prow/e2e-aws-tests 89ff01d link true /test e2e-aws-tests
ci/prow/e2e-aws-tests-release 89ff01d link true /test e2e-aws-tests-release
ci/prow/e2e-aws-tests-release-arm 89ff01d link true /test e2e-aws-tests-release-arm
ci/prow/e2e-aws-tests-bootc-release-el10 89ff01d link true /test e2e-aws-tests-bootc-release-el10
ci/prow/e2e-aws-tests-bootc-el9 89ff01d link true /test e2e-aws-tests-bootc-el9

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants